Method and apparatus for quality of service handling in wireless communication system

ABSTRACT

A method performed by a user equipment (UE)-to-network relay in a wireless communication system is provided. The method includes, in case that PC5 quality of service (QoS) flows setup is initiated by a remote UE, identifying whether QoS requirements associated with the remote UE and the UE-to-network relay are supported, in case that the QoS requirements are not supported, identifying one or more QoS parameters that satisfy the QoS requirements, and based on the one or more QoS parameters, updating a PC5 QoS flow.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is based on and claims priority under 35 U.S.C. §119(a) of a Great Britain patent application number 2007435.7, filed onMay 19, 2020, in the Intellectual Property Office, and of a GreatBritain patent application number 2106639.4, filed on May 10, 2021, inthe Intellectual Property Office, the disclosure of each of which isincorporated by reference herein in its entirety.

BACKGROUND 1. Field

The disclosure relates to the quality of service (QoS) handling forproximity services (ProSe) where a user equipment (UE)-to-Network Relayentity provides the functionality to support connectivity to the networkfor Remote UEs.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4^(th) generation (4G) communication systems, efforts havebeen made to develop an improved 5^(th) generation (5G) or pre-5Gcommunication system. The 5G or pre-5G communication system is alsocalled a ‘beyond 4G network’ or a ‘post long term evolution (LTE)system’. The 5G communication system is considered to be implemented inhigher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplishhigher data rates. To decrease propagation loss of the radio waves andincrease the transmission distance, beamforming, massive multiple-inputmultiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna,analog beamforming, and large scale antenna techniques are discussedwith respect to 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud radio access networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,coordinated multi-points (CoMP), reception-end interference cancellationand the like. In the 5G system, hybrid frequency shift keying (FSK) andFeher's quadrature amplitude modulation (FQAM) and sliding windowsuperposition coding (SWSC) as an advanced coding modulation (ACM), andfilter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA),and sparse code multiple access (SCMA) as an advanced access technologyhave been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofeverything (IoE), which is a combination of the IoT technology and thebig data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “security technology” have been demanded forIoT implementation, a sensor network, a machine-to-machine (M2M)communication, machine type communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing information technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies, suchas a sensor network, MTC, and M2M communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RAN as theabove-described big data processing technology may also be considered tobe as an example of convergence between the 5G technology and the IoTtechnology.

As described above, various services can be provided according to thedevelopment of a wireless communication system, and thus a method foreasily providing such services is required.

The above information is presented as background information only toassist with an understanding of the disclosure. No determination hasbeen made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the disclosure.

SUMMARY

Aspects of the disclosure are to address at least the above-mentionedproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the disclosure is to providea method for easily providing various services according to thedevelopment of a wireless communication system.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented embodiments.

In accordance with an aspect of the disclosure, a method performed by auser equipment (UE)-to-network relay in a wireless communication systemis provided. The method includes, in case that PC5 quality of service(QoS) flows setup is initiated by a remote UE, identifying whether QoSrequirements associated with the remote UE and the UE-to-network relayare supported, in case that the QoS requirements are not supported,identifying one or more QoS parameters that satisfy the QoSrequirements, and based on the one or more QoS parameters, updating aPC5 QoS flow.

In accordance with another aspect of the disclosure, a method performedby a user equipment (UE)-to-network relay in a wireless communicationsystem is provided. The method includes transmitting, to a policycontrol function (PCF) via a session management function (SMF),information associated with at least one quality of service (QoS)requirement, receiving, from the PCF via the SMF, one or more PC5 QoSparameters, and initiating a layer-2 link modification procedure basedon the one or more PC5 QoS parameters.

In accordance with another aspect of the disclosure, a user equipment(UE)-to-network relay in a wireless communication system is provided.The UE-to-network relay includes a transceiver, and at least oneprocessor configured to, in case that PC5 quality of service (QoS) flowssetup is initiated by a remote UE, identify whether QoS requirementsassociated with the remote UE and the UE-to-network relay are supported,in case that the QoS requirements are not supported, identify one ormore QoS parameters that satisfy the QoS requirements, and based on theone or more QoS parameters, update a PC5 QoS flow.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the disclosure will be more apparent from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a traffic relay system according to an embodiment ofthe disclosure;

FIG. 2 illustrates a representation of a call flow according to anembodiment of the disclosure;

FIG. 3 illustrates a representation of a call flow according to anembodiment of the disclosure;

FIG. 4 illustrates a representation of a call flow according to anembodiment of the disclosure;

FIG. 5 is a diagram illustrating UE-to network relay according to anembodiment of the disclosure;

FIG. 6 is a diagram illustrating a user equipment according to anembodiment of the disclosure; and

FIG. 7 is a diagram illustrating a core network entity according to anembodiment of the disclosure.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thedisclosure. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of thedisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of thedisclosure is provided for illustration purpose only and not for thepurpose of limiting the disclosure as defined by the appended claims andtheir equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

Throughout the disclosure, the expression “at least one of a, b or c”indicates only a, only b, only c, both a and b, both a and c, both b andc, all of a, b, and c, or variations thereof. Throughout thespecification, a layer (or a layer apparatus) may also be referred to asan entity. Hereinafter, operation principles of the disclosure will bedescribed with reference to accompanying drawings. In the followingdescriptions, well-known functions or configurations are not describedbecause they would obscure the disclosure with unnecessary details. Theterms used in the specification are defined based on functions used inthe disclosure, and can be changed according to the intent or commonlyused methods of users or operators. Accordingly, definitions of theterms are understood based on the entire descriptions of the presentspecification.

For the same reasons, in the drawings, some elements may be exaggerated,omitted, or roughly illustrated. In addition, a size of each elementdoes not exactly correspond to an actual size of each element. In eachdrawing, elements that are the same or are in correspondence arerendered the same reference numeral.

Advantages and features of the disclosure and methods of accomplishingthe same may be understood more readily by reference to the followingdetailed descriptions of embodiments and accompanying drawings of thedisclosure. The disclosure may, however, be embodied in many differentforms and should not be construed as being limited to the embodimentsset forth herein; rather, these embodiments of the disclosure areprovided so that this disclosure will be thorough and complete, and willfully convey the concept of the disclosure to one of ordinary skill inthe art. Therefore, the scope of the disclosure is defined by theappended claims. Throughout the specification, like reference numeralsrefer to like elements. It will be understood that blocks in flowchartsor combinations of the flowcharts may be performed by computer programinstructions. Because these computer program instructions may be loadedinto a processor of a general-purpose computer, a special-purposecomputer, or another programmable data processing apparatus, theinstructions, which are performed by a processor of a computer oranother programmable data processing apparatus, create units forperforming functions described in the flowchart block(s).

The computer program instructions may be stored in a computer-usable orcomputer-readable memory capable of directing a computer or anotherprogrammable data processing apparatus to implement a function in aparticular manner, and thus the instructions stored in thecomputer-usable or computer-readable memory may also be capable ofproducing manufactured items containing instruction units for performingthe functions described in the flowchart block(s). The computer programinstructions may also be loaded into a computer or another programmabledata processing apparatus, and thus, instructions for operating thecomputer or the other programmable data processing apparatus bygenerating a computer-executed process when a series of operations areperformed in the computer or the other programmable data processingapparatus may provide operations for performing the functions describedin the flowchart block(s).

In addition, each block may represent a portion of a module, segment, orcode that includes one or more executable instructions for executingspecified logical function(s). It is also noted that, in somealternative implementations, functions mentioned in blocks may occur outof order. For example, two consecutive blocks may also be executedsimultaneously or in reverse order depending on functions correspondingthereto.

As used herein, the term “unit” denotes a software element or a hardwareelement, such as a field-programmable gate array (FPGA) or anapplication-specific integrated circuit (ASIC), and performs a certainfunction. However, the term “unit” is not limited to software orhardware. The “unit” may be formed so as to be in an addressable storagemedium, or may be formed so as to operate one or more processors. Thus,for example, the term “unit” may include elements (e.g., softwareelements, object-oriented software elements, class elements, and taskelements), processes, functions, attributes, procedures, subroutines,segments of program code, drivers, firmware, micro-codes, circuits,data, a database, data structures, tables, arrays, or variables.

Functions provided by the elements and “units” may be combined into thesmaller number of elements and “units”, or may be divided intoadditional elements and “units”. Furthermore, the elements and “units”may be embodied to reproduce one or more central processing units (CPUs)in a device or security multimedia card. In addition, in an embodimentof the disclosure, the “unit” may include at least one processor. In thefollowing descriptions of the disclosure, well-known functions orconfigurations are not described because they would obscure thedisclosure with unnecessary details.

Hereinafter, for convenience of explanation, the disclosure uses termsand names defined in the 3rd generation partnership project long termevolution (3GPP LTE) standards. However, the disclosure is not limitedto the terms and names, and may also be applied to systems followingother standards.

In the disclosure, an evolved node B (eNB) may be interchangeably usedwith a next-generation node B (gNB) for convenience of explanation. Forexample, a base station (BS) described by an eNB may represent a gNB. Inthe following descriptions, the term “base station” refers to an entityfor allocating resources to a user equipment (UE) and may be usedinterchangeably with at least one of a gNode B, an eNode B, a node B, abase station (BS), a radio access unit, a base station controller (BSC),or a node over a network. The term “terminal” may be usedinterchangeably with a user equipment (UE), a mobile station (MS), acellular phone, a smartphone, a computer, or a multimedia system capableof performing communication functions. However, the disclosure is notlimited to the aforementioned examples. In particular, the disclosure isapplicable to 3GPP new radio (NR) (or 5^(th) generation (5G)) mobilecommunication standards. In the following description, the term eNB maybe interchangeably used with the term gNB for convenience ofexplanation. For example, a base station explained as an eNB may alsoindicate a gNB. The term UE may also indicate a mobile phone, NB-IoTdevices, sensors, and other wireless communication devices.

Proximity Services (ProSe) (specifically the direct communication) havebeen enhanced to support vehicle to everything (V2X) services over LTE.For Fifth Generation Systems (5GS), the proximity services are expectedto be an important system-wide enabler to support various applicationsand services.

Another class of commercial services has recently emerged known asNetwork-controlled Interactive services (NCIS) that share somecommonality of requirements with public safety services andapplications. NCIS refers to a kind of service which needs at least 2user equipment (UE) to join and share data, e.g., interactive gaming ordata sharing. Those UEs in the same NCIS session are grouped together asone NCIS group, and the group is determined by application layer (i.e.,NCIS application server).

In order to guarantee service requirements, QoS parameters are derivedbased on proximity application requirements; QoS flows and correspondingQoS rules are created accordingly. However, in the presence of a relay,this is not trivial and involves performing QoS control for PC5interface between Remote UE and UE-to-Network Relay as well as QoScontrol over protocol data unit (PDU) session established between theUE-to-Network Relay and the Network via Uu interface.

FIG. 1 shows an example of how ProSe UE-to-Network Relay 20 relaystraffic (uplink (UL) and downlink (DL)) between the Remote UE 10 and theNetwork (comprising NG-Radio Access Network (RAN) 30, 5G Core (5GC) 40,and Application Server (AS) 50).

The terms ProSe UE-to-Network Relay and UE-to-Network Relay or, simply,relay are used interchangeably throughout the disclosure, as will beunderstood by the skilled person.

Embodiments of the disclosure aim to address shortcomings in the priorart, whether mentioned herein or not.

According to a first aspect of the disclosure, there is provided amethod of managing Quality of Service, QoS, in a telecommunicationsystem comprising a user equipment (UE), which is operable tocommunicate with a network via a UE to network relay, wherein the QoS ismanaged in response to at least one trigger derived from one or more ofa remote UE, a ProSe UE to network Relay, radio access network (RAN),and an application server.

In an embodiment of the disclosure, the at least one trigger is basedon, or derived from, one or more of link status between a remote UE anda ProSe UE-to-network relay, Uu Congestion status or other indicationson QoS fulfilment from RAN, and policy controls derived from ApplicationSever, either for public safety applications or for network-controlledinteractive services (NCIS).

In an embodiment of the disclosure, the QoS management is in response toa trigger from either the remote UE or ProSe UE to network Relay over aPC5 interface.

In an embodiment of the disclosure, a QoS mapping configuration ispreconfigured on one or more of the UE and ProSe UE to network Relay oris provisioned by a user configuration Update via PCF.

In an embodiment of the disclosure, the QoS mapping configurationindicates how Uu-level QoS flows are mapped to PC5 QoS flows and/orvice-versa.

In an embodiment of the disclosure, an entry in the QoS mappingconfiguration includes an adjustment factor to be applied per individualQoS characteristics when mapping is performed.

In an embodiment of the disclosure, if there is a degradation in achannel state, either the UE or ProSe UE to network Relay identifiesthat QoS requirements over the link between the UE and ProSe UE tonetwork Relay cannot be met, reflecting that end-to-end QoS requirementscannot be met.

In an embodiment of the disclosure, the ProSe UE to network Relayinitiates a remote UE report to SMF including Remote User ID, IPinformation or any other relevant address information, indicating thehighest priority Alternative QoS profile that can be fulfilled, meetingend-end QoS requirements.

In an embodiment of the disclosure, the UE or ProSe UE to network Relayuses Layer-2 link modification procedure to modify PC5 QoS flow in linewith the Alternative QoS Profile adopted.

In an embodiment of the disclosure, as part of the Layer-2 linkmodification procedure, PC5 QoS rules are updated with additionalinformation elements either implicitly or explicitly, reflecting achange in the end-to-end QoS requirements.

In an embodiment of the disclosure, the SMF forwards the remote UEreport to PCF.

In an embodiment of the disclosure, the SMF initiates a transparentnetwork access stratum (NAS) update towards RAN to amend Uu-level QoSflows treatment between RAN and a ProSe UE-to-Network relay or to changePC5-level cap on link transmission based on new ProSe configuration andpolicy parameters or Alternative QoS profile over PC5.

In an embodiment of the disclosure, on ProSe AF request, a UE or a ProSeUE to network Relay receives a user configuration update from PCF (80)to notify new ProSe configuration and policy parameters.

In an embodiment of the disclosure, either a ProSe UE to network Relayestablishes a new PDU session or modifies an existing PDU session forrelaying; or PCF initiates a PDU session modification.

According to a second aspect of the disclosure, there is providedapparatus arranged to perform the method of the first aspect.

Although a few preferred embodiments of the disclosure have been shownand described, it will be appreciated by those skilled in the art thatvarious changes and modifications might be made without departing fromthe scope of the disclosure, as defined in the appended claims.

For a better understanding of the disclosure, and to show howembodiments of the same may be carried into effect, reference will nowbe made, by way of example only, to the accompanying diagrammaticdrawings in which:

FIG. 1 illustrates a traffic relay system according to an embodiment ofthe disclosure.

FIG. 2 illustrates a representation of a call flow according to anembodiment of the disclosure.

FIG. 3 illustrates a representation of a call flow according to anembodiment of the disclosure.

FIG. 4 illustrates a representation of a call flow according to anembodiment of the disclosure.

FIG. 2 , and the following figures, show various network functionsand/or entities, whose functions and definitions are known in the art inat least: 3GPP TS 23.501, 3GPP TS 23.502 and 3GPP TS 23.503. The variousknown functions of these network functions/entities are varied and/orenhanced as set out in the following description.

For completeness, the various functions/entities shown are: a userequipment (UE) (10), a next generation radio access network (NG-RAN)(30), a session management function (SMF) (60), a user policy function(UPF) (70), a policy control function (PCF) (80), and an applicationfunction (AF) (90).

Referring to FIG. 2 , SMF (60), UPF (70), PCF (80) are constituent partsof 5GC (40). AF (90) is equivalent to AS (50).

Unless explicitly indicated, PCF 80 refers to the policy controlfunction utilized for UE policy and access and mobility (AM) policyassociation. Otherwise, when stated (session management (SM) Policy) PCF80 refers to the policy control function utilized for SM policyassociation. Both policy functions may be co-located dependent on thedeployment and the selection criteria.

FIG. 2 illustrates a first scenario according to an embodiment of thedisclosure. This embodiment relates to QoS control based on a triggerfrom Remote UE/ProSe UE-to-Network Relay over the PC5 Interface. In thisscenario, it is assumed that ProSe configuration and policy parametersincluding QoS mapping configuration have been pre-configured on theRemote UE 10 (and UE-to-Network Relay 20) or provisioned by UserConfiguration Update via PCF 80 e.g., based on ProSe AF request. A QoSmapping table indicates how Uu-level QoS flows (i.e., 5G QoSIdentifiers—5QIs) can be mapped to PC5 QoS flows (i.e., PC5 QoSIdentifiers—PQIs) or vice versa. Each entry in the table may alsoinclude an adjustment factor to be applied per individual QoScharacteristics (e.g., packet delay budget) within 5QIs and/or PQIs whenmapping 5QIs to PQIs or vice versa.

Details of each operation shown in FIG. 2 are:

S21. Due to degradation in the channel state, based on L1/L2measurements or other indications on PC5-U/PC5-S (e.g., due to a changeof service, resulting in a new end-to-end QoS requirement), eitherRemote UE 10 or UE-to-network relay 20 identifies that the QoSrequirements over PC5 cannot be fulfilled anymore.

For example, in operation S21, the UE 10 or UE-to-network relay 20 mayidentify that the QoS requirements over PC5 are not supported. In anembodiment of the disclosure, the UE 10 may identify that QoSrequirements over PC5 are not supported and transmit, to theUE-to-network relay, information associated with at least one QoSrequirement. The information associated with the at least one QoSrequirements may indicate that the QoS requirements over PC5 are notsupported.

S22. UE-to-Network Relay 20 may initiate a Remote UE report to SMF 60(e.g., via NG-RAN 30) including Remote User ID, IP information or anyother relevant information, indicating that the QoS profile cannot befulfilled. A further Remote UE report to SMF 60 can be initiated in casethe QoS profile can be fulfilled again in future.

For example, in operation S22, the UE-to-Network Relay 20 may transmit,to the SMF, the information associated with the at least one QoSrequirements indicating that the QoS requirements over PC5 are notsupported. In an embodiment of the disclosure, the informationassociated with the at least one QoS requirements may be transmittedfrom the UE-to-Network Relay 20 to the SMF 60 via Remote UE report.

S23. [Conditional in support of an Alternative QoS over PC5, ordepending on the implementation] UE-to-Network Relay 20 may initiate aRemote UE report to SMF 60 (e.g., via NG-RAN 30) including Remote UserID, IP information or any other relevant address information, indicatingthe highest priority Alternative QoS profile that can be fulfilledmeeting end-to-end QoS requirements. Remote UE 10 (and/or UE-to-NetworkRelay 20) may use Layer-2 link modification procedure to modify PC5 QoSflow(s) in line with the Alternative QoS Profile adopted. If noAlternative QoS profile matches the current channel state, the procedurewould be similar to operation S22, described above.

In an embodiment of the disclosure, the UE-to-Network Relay 20 mayidentify one or more QoS parameters that satisfy the QoS requirementsand transmit, to the PCF 80 via the SMF 60, information associated withthe one or more QoS parameters. Based on an authorization of the one ormore QoS parameters performed by the PCF 80, the UE-to-Network Relay 20may update a PC5 QoS flow via the Layer-2 link modification procedure.

As part of Layer-2 link modification to PC5 QoS flow(s), the PC5 QoSrules can be updated with additional information elements eitherimplicitly or explicitly (to be stored as part of UE PC5 QoS context),reflecting change in end-to-end QoS requirements e.g., updated PQI/5QI,updated adjustment factor per QoS characteristics within PQI/5QI,updated end-to-end Packet delay budget, updated priority level, updatedpacket error rate, updated averaging window, updated maximum data burstvolume or any other PC5 QoS characteristics. Such additional informationmay override the default QoS characteristics.

S24. SMF 60 may forward the notification to (SM Policy) PCF 80. ProSe AF90 may also be notified based on a former subscription to (SM Policy)PCF 80. ProSe AF 90 may update the relevant ProSe configuration andpolicy parameters.

In an embodiment of the disclosure, the PCF 80 may identify one or morePC5 QoS parameters and transmit, to the UE-to-Network Relay 20 via theSMF 60, information associated with the one or more PC5 QoS parameters.

S25. Unless notified differently by (SM Policy) PCF 80, SMF 60 mayinitiate a transparent network access stratum (NAS) update towardsNG-RAN 30, e.g., to amend Uu-level QoS flows treatment between NG-RAN 30and UE-to-Network Relay 20 (e.g., to update packet delay budget) or tochange PC5-level cap on link transmission based on new ProSeconfiguration and policy parameters or alternative QoS profile over PC5(if supported, or depending on the implementation).

S26. On ProSe AF request, a remote UE 10 (and/or UE-to-Network Relay 20)may receive a user configuration update (via PCF 80) to notify on newProSe configuration and policy parameters. Remote UE 10 (and/orUE-to-Network Relay 20) may use Layer-2 link modification procedure tomodify PC5 QoS flow(s) in line with Configuration Update.

In an embodiment of the disclosure, in operation S26, the UE-to-NetworkRelay 20 may initiate the Layer-2 link modification procedure based onthe one or more PC5 QoS parameters. For example, the UE-to-Network Relay20 may update PC5 QoS flows via the Layer-2 link modification procedure.

S27. (a) UE-to-Network Relay 20 may establish a new PDU session ormodify an existing PDU session for relaying. (b) Alternatively, PCF 80may initiate PDU session modification.

FIG. 3 illustrates a second scenario according to an embodiment of thedisclosure. This embodiment relates to a Network-Assisted QoS controlover Uu interface. In this scenario, it is assumed that ProSeconfiguration and policy parameters including QoS mapping configurationhave been pre-configured on Remote UE 10 (and UE-to-Network Relay 20) orprovisioned by user configuration update via PCF 80 e.g., based on ProSeAF request. It is also assumed that Remote User ID is already registeredin SMF 60 via a Remote UE report.

Details of each operation in FIG. 3 are:

S31. NG-RAN 30 may detect that QoS requirements cannot be fulfilled forone or more QoS Flows (towards UE-to-Network Relay 20 via Uu interface).

S32. NG-RAN 30 may initiate a QoS notification (QNC) to SMF 60. (If anAlternative QoS can be supported over Uu), the highest priorityAlternative QoS profile can be indicated.

S33. Based on Remote User ID(s) implicated by this QNC, SMF 60 mayidentify that ProSe configuration parameters or QoS Profile (e.g., overPC5) should be changed.

S34. SMF 60 may forward the QoS notification to (SM Policy) PCF 80.ProSe AF 90 may also be notified based on a former subscription to (SMPolicy) PCF 80 to update relevant ProSe configuration and policyparameters.

S35. Unless notified differently by (SM Policy) PCF 80, SMF 60 mayinitiate a transparent NAS update towards NG-RAN 30, e.g., to amendUu-level QoS flows treatment between NG-RAN 30 and UE-to-Network Relay20 (e.g., to update Packet Delay Budget) or to change PC5-level cap onlink transmission based on new ProSe configuration and policy parametersor an Alternative QoS profile adopted over Uu (if supported).

S36. On ProSe AF 90 request, Remote UE 10 (and/or UE-to-Network Relay20) may receive a user configuration update (via PCF 80) to notify onnew ProSe configuration and policy parameters. Remote UE 10 (and/orUE-to-Network Relay 20) may use Layer-2 link modification procedure tomodify PC5 QoS flow(s).

S37. (a) UE-to-Network Relay 20 may establish a new PDU session ormodify an existing PDU session for relaying. (b) Alternatively PCF 80may initiate PDU session modification.

FIG. 4 illustrates a third scenario according to an embodiment of thedisclosure. This embodiment relates to an AF-assisted QoS control. It isassumed that ProSe configuration and policy parameters including QoSmapping configuration have been pre-configured on Remote UE 10 (andUE-to-Network Relay 20) or provisioned by User Configuration Update viaPCF 80 e.g., based on ProSe AF request. Furthermore, ProSe AF 90 mayaccess analytics data from NWDAF 100 (not shown).

Details of each operation in FIG. 4 are:

S41. ProSe AF 90 may identify that all QoS requirements cannot befulfilled for one or more QoS Flows e.g., based on (a) Remote UEmobility, (b) topology or requirement changes or (c) any analyticsnotification (either as statistics or prediction) from NWDAF 100 (e.g.,on QoS sustainability or service experience).

S42. On ProSe AF 90 request, Remote UE 10 (and/or UE-to-Network Relay20) may receive a User Configuration Update (via PCF 80) to notify onnew ProSe configuration and policy parameters or an alternative QoSprofile to use over PC5 (if supported or depending on theimplementation). Remote UE 10 (and/or UE-to-Network Relay 20) may useLayer-2 link modification procedure to modify PC5 QoS flow(s).

S43. (a) UE-to-Network Relay 20 may establish a new PDU session ormodify an existing PDU session for relaying. (b) Alternatively PCF 80may initiate PDU session modification.

FIG. 5 is a diagram illustrating UE-to-network relay according to anembodiment of the disclosure.

Referring to the FIG. 5 , the UE-to-network relay 500 may include aprocessor 510, a transceiver 520 and a memory 530. However, all of theillustrated components are not essential. The UE-to-network relay 500may be implemented by more or less components than those illustrated inthe FIG. 5 . In addition, the processor 510 and the transceiver 520 andthe memory 530 may be implemented as a single chip according to anotherembodiment.

The aforementioned components will now be described.

The processor 510 may include one or more processors or other processingdevices that control the proposed function, process, and/or method.Operation of the UE-to-network relay 500 may be implemented by theprocessor 610.

The transceiver 520 may be connected to the processor 510 and transmitand/or receive a signal. In addition, the transceiver 520 may receivethe signal through a wireless channel and output the signal to theprocessor 510. The transceiver 520 may transmit the signal output fromthe processor 510 through the wireless channel.

The memory 530 may store the control information or the data included ina signal obtained by the UE-to-network relay 500. The memory 530 may beconnected to the processor 510 and store at least one instruction or aprotocol or a parameter for the proposed function, process, and/ormethod. The memory 530 may include a read-only memory (ROM) and/or arandom access memory (RAM) and/or hard disk and/or a compact disc readonly memory (CD-ROM) and/or a digital versatile disc (DVD) and/or otherstorage devices.

FIG. 6 is a diagram illustrating a user equipment according to anembodiment of the disclosure.

Referring to the FIG. 6 , the UE 600 may include a processor 610, atransceiver 620 and a memory 630. However, all of the illustratedcomponents are not essential. The UE 600 may be implemented by more orless components than those illustrated in the FIG. 6 . In addition, theprocessor 610 and the transceiver 620 and the memory 630 may beimplemented as a single chip according to another embodiment.

The aforementioned components will now be described.

The processor 610 may include one or more processors or other processingdevices that control the proposed function, process, and/or method.Operation of the UE 600 may be implemented by the processor 610.

The transceiver 620 may be connected to the processor 610 and transmitand/or receive a signal. In addition, the transceiver 620 may receivethe signal through a wireless channel and output the signal to theprocessor 610. The transceiver 620 may transmit the signal output fromthe processor 610 through the wireless channel.

The memory 630 may store the control information or the data included ina signal obtained by the UE 600. The memory 630 may be connected to theprocessor 610 and store at least one instruction or a protocol or aparameter for the proposed function, process, and/or method. The memory630 may include a read-only memory (ROM) and/or a random access memory(RAM) and/or a hard disk and/or a CD-ROM and/or a DVD and/or otherstorage devices.

FIG. 7 is a diagram illustrating a core network entity according to anembodiment of the disclosure.

The NG-RAN 30, 5GC 40 and application server 50 described above maycorrespond to the core network entity 700.

Referring to the FIG. 7 , the core network entity 700 may include aprocessor 710, a transceiver 720 and a memory 730. However, all of theillustrated components are not essential. The core network entity 700may be implemented by more or less components than those illustrated inFIG. 7 . In addition, the processor 710 and the transceiver 720 and thememory 730 may be implemented as a single chip according to anotherembodiment.

The aforementioned components will now be described.

The transceiver 720 may provide an interface for performingcommunication with other devices in a network. For example, thetransceiver 720 may convert a bitstream transmitted from the corenetwork entity 700 to other devices to a physical signal and covert aphysical signal received from other devices to a bitstream. For example,the transceiver 720 may transmit and receive a signal. The transceiver720 may be referred to as modem, transmitter, receiver, communicationunit and communication module. The transceiver 720 may enable the corenetwork entity 700 to communicate with other devices or system throughbackhaul connection or other connection method.

The memory 730 may store a basic program, an application program,configuration information for an operation of the core network entity700. The memory 730 may include volatile memory, non-volatile memory anda combination of the volatile memory and the non-volatile memory. Thememory 730 may provide data according to a request from the processor710.

The processor 710 may control overall operations of the core networkentity 400. For example, the processor 710 may transmit and receive asignal through the transceiver 720. The processor 710 may include atleast one processor. The processor 710 may control the core networkentity 700 to perform operations according to embodiments of thedisclosure.

In accordance with an embodiment of the disclosure, a method of managingquality of service (QoS) in a telecommunication system is provided. Themethod may comprise a user equipment (UE) (10), which is operable tocommunicate with a network via a UE to network relay (20), wherein theQoS is managed in response to at least one trigger derived from one ormore of a) a remote UE (10), b) a ProSe UE to network relay (20), c) aradio access network (RAN) (30), and d) an application server (50).

In an embodiment of the disclosure, wherein the at least one trigger isbased on, or derived from, one or more of a) a link status betweenremote UE (10) and a ProSe UE-to-network relay (20), b) Uu Congestionstatus or other indications on QoS fulfilment from RAN (30), and c)Policy controls derived from an application server (50), either forpublic safety applications or for network-controlled interactiveservices, NCIS.

In an embodiment of the disclosure, wherein the QoS management is inresponse to a trigger from either the remote UE (10) or ProSe UE tonetwork relay (20) over a PC5 interface.

In an embodiment of the disclosure, wherein a QoS mapping configurationis preconfigured on one or more of the UE (10) and ProSe UE to networkRelay (20) or is provisioned by a user configuration update via PCF(80).

In an embodiment of the disclosure, wherein the QoS mappingconfiguration indicates how Uu-level QoS flows are mapped to PC5 QoSflows and/or vice-versa.

In an embodiment of the disclosure, wherein an entry in the QoS mappingconfiguration includes an adjustment factor to be applied per individualQoS characteristics when mapping is performed.

In an embodiment of the disclosure, wherein, if there is a degradationin a channel state, either the UE (10) or ProSe UE to network Relay (20)identifies that QoS requirements over the link between the UE (10) andProSe UE to network Relay (20) cannot be met, reflecting that end-to-endQoS requirements cannot be met.

In an embodiment of the disclosure, wherein the ProSe UE to networkRelay (20) initiates a remote UE report to SMF (60) including RemoteUser ID, IP information or any other relevant address information,indicating the highest priority Alternative QoS profile that can befulfilled, meeting end-end QoS requirements.

In an embodiment of the disclosure, wherein the UE (10) or ProSe UE tonetwork Relay (20) uses Layer-2 link modification procedure to modifyPC5 QoS flow in line with the Alternative QoS Profile adopted.

In an embodiment of the disclosure, wherein as part of the Layer-2 linkmodification procedure, PC5 QoS rules are updated with additionalinformation elements either implicitly or explicitly, reflecting achange in the end-to-end QoS requirements.

In an embodiment of the disclosure, wherein the SMF (60) forwards theremote UE report to PCF (80).

In an embodiment of the disclosure, wherein the SMF (60) initiates atransparent network access stratum (NAS), update towards RAN (30) toamend Uu-level QoS flows treatment between RAN (30) and ProSeUE-to-network relay (20) or to change PC5-level cap on link transmissionbased on new ProSe configuration and policy parameters or AlternativeQoS profile over PC5.

In an embodiment of the disclosure, wherein on ProSe AF (90) request, UE(10) or ProSe UE to network Relay (20) receives a user configurationupdate from PCF (80) to notify new ProSe configuration and policyparameters.

In an embodiment of the disclosure, wherein either: ProSe UE to networkrelay (20) establishes a new PDU session or modifies an existing PDUsession for relaying, or a PCF (80) initiates a PDU sessionmodification.

In an embodiment of the disclosure, apparatus is arranged to perform themethod.

In accordance with an embodiment of the disclosure, a method performedby a user equipment (UE)-to-network relay in a wireless communicationsystem is provided. The method may comprise in case that PC5 quality ofservice (QoS) flows setup is initiated by a remote UE, identifyingwhether QoS requirements associated with the remote UE and theUE-to-network relay are supported, in case that the QoS requirements arenot supported, identifying one or more QoS parameters that satisfy theQoS requirements, and based on the one or more QoS parameters, updatinga PC5 QoS flow.

In an embodiment of the disclosure, the method may further comprisetransmitting, to a policy control function (PCF), information associatedwith the one or more QoS parameters.

In an embodiment of the disclosure, the updating of the PC5 QoS flow maycomprises: updating the PC5 QoS flow based on an authentication of theone or more QoS parameters.

In an embodiment of the disclosure, the method may further comprisereceiving, from a PCF, information associated with QoS mapping rules.

In an embodiment of the disclosure, wherein information associated withQoS mapping rules for the UE-to-network relay is pre-configured.

In an embodiment of the disclosure, wherein the PC5 QoS flow is updatedvia a layer-2 link modification procedure.

In accordance with an embodiment of the disclosure, a method performedby a user equipment (UE)-to-network relay in a wireless communicationsystem is provided. The method may comprise transmitting, to a policycontrol function (PCF) via a session management function (SMF),information associated with at least one quality of service (QoS)requirement, receiving, from the PCF via the SMF, one or more PC5 QoSparameters, and initiating a layer-2 link modification procedure basedon the one or more PC5 QoS parameters.

In an embodiment of the disclosure, wherein the information associatedwith the at least one quality of service (QoS) requirement is receivedfrom a remote UE.

In an embodiment of the disclosure, wherein the information associatedwith the at least one quality of service (QoS) requirement istransmitted to the SMF via a remote UE report.

In an embodiment of the disclosure, wherein the layer-2 linkmodification is used to update PC5 QoS flows.

In an embodiment of the disclosure, wherein a QoS flow setup isinitiated by the SMF.

In accordance with an embodiment of the disclosure, a user equipment(UE)-to-network relay in a wireless communication system is provided.The UE-to-network relay may comprise: a transceiver, and at least oneprocessor configured to in case that PC5 quality of service (QoS) flowssetup is initiated by a remote UE, identify whether QoS requirementsassociated with the remote UE and the UE-to-network relay are supported,in case that the QoS requirements are not supported, identify one ormore QoS parameters that satisfy the QoS requirements, and based on theone or more QoS parameters, update a PC5 QoS flow.

In an embodiment of the disclosure, the at least one processor isfurther configured to transmit, to a policy control function (PCF) viathe transceiver, information associated with the one or more QoSparameters.

In an embodiment of the disclosure, the at least one processor isfurther configured to update the PC5 QoS flow based on an authenticationof the one or more QoS parameters.

In an embodiment of the disclosure, the at least one processor isfurther configured to receive, from a PCF via the transceiver,information associated with QoS mapping rules.

Note that in all embodiments described above, based on new ProSeconfiguration and policy parameters, Remote UE 10 may alternativelydecide to run a new discovery procedure to find another UE-to-NetworkRelay 20′. Remote UE 10 may use Layer-2 link modification procedure toremove PC5 QoS flow(s). If so, a Remote UE Report may be sent (e.g., viaexisting UE-to-Network Relay 20) to inform the SMF 60 that the Remote UE10 is going to leave. Corresponding PDU session (of existingUE-to-Network Relay 20) can be modified or released dependent onimplementation criteria.

Although presented in terms of ProSe and 5GC, the skilled person willreadily appreciate that other network topologies and/or protocols whichrely on direct communication between UEs and also network-assistedcommunication between the same devices will benefit from embodiments ofthe disclosure.

At least some of the example embodiments described herein may beconstructed, partially or wholly, using dedicated special-purposehardware. Terms, such as ‘component’, ‘module’ or ‘unit’ used herein mayinclude, but are not limited to, a hardware device, such as circuitry inthe form of discrete or integrated components, a field programmable gatearray (FPGA) or application specific integrated Circuit (ASIC), whichperforms certain tasks or provides the associated functionality. In someembodiments of the disclosure, the described elements may be configuredto reside on a tangible, persistent, addressable storage medium and maybe configured to execute on one or more processors. These functionalelements may in some embodiments include, by way of example, components,such as software components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables. Although the example embodiments have been described withreference to the components, modules and units discussed herein, suchfunctional elements may be combined into fewer elements or separatedinto additional elements. Various combinations of optional features havebeen described herein, and it will be appreciated that describedfeatures may be combined in any suitable combination. In particular, thefeatures of any one example embodiment may be combined with features ofany other embodiment of the disclosure, as appropriate, except wheresuch combinations are mutually exclusive. Throughout this specification,the term “comprising” or “comprises” means including the component(s)specified but not to the exclusion of the presence of others.

Attention is directed to all papers and documents which are filedconcurrently with or previous to this specification in connection withthis application and which are open to public inspection with thisspecification, and the contents of all such papers and documents areincorporated herein by reference.

All of the features disclosed in this specification (including anyaccompanying claims, abstract and drawings), and/or all of theoperations of any method or process so disclosed, may be combined in anycombination, except combinations where at least some of such featuresand/or operations are mutually exclusive.

Each feature disclosed in this specification (including any accompanyingclaims, abstract and drawings) may be replaced by alternative featuresserving the same, equivalent or similar purpose, unless expressly statedotherwise. Thus, unless expressly stated otherwise, each featuredisclosed is one example only of a generic series of equivalent orsimilar features.

While the disclosure has been shown and described with reference tovarious embodiments thereof, it will be understood by those skilled inthe art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the disclosure as definedby the appended claims and their equivalents.

What is claimed is:
 1. A method performed by a user equipment(UE)-to-network relay in a wireless communication system, the methodcomprising: identifying that quality of service (QoS) requirementsassociated with a PC5 QoS flow are not supported, based on QoSinformation associated with the PC5 QoS flow; based on the identifying,determining one or more QoS parameters for a QoS control; andtransmitting, to a remote UE, information associated with the determinedone or more QoS parameters.
 2. The method of claim 1, furthercomprising: transmitting, to a core network entity, the informationassociated with the one or more QoS parameters.
 3. The method of claim2, further comprising: updating the PC5 QoS flow based on anauthentication by a policy control function (PCF) entity for the one ormore QoS parameters.
 4. The method of claim 1, further comprising:receiving, from a core network entity, information associated with QoSmapping rules.
 5. The method of claim 1, wherein the UE-to-network relayis pre-configured with information associated with QoS mapping rules. 6.The method of claim 1, wherein the information associated with the oneor more QoS parameters is transmitted via a layer-2 link modificationprocedure for modifying the PC5 QoS flow.
 7. A user equipment(UE)-to-network relay in a wireless communication system, theUE-to-network relay comprising: a transceiver; and at least oneprocessor configured to: identify that quality of service (QoS)requirements associated with a PC5 QoS flow are not supported, based onQoS information associated with the PC5 QoS flow, based on theidentification, determine one or more QoS parameters for a QoS control,and transmit, to a remote UE via the transceiver, information associatedwith the determined one or more QoS parameters.
 8. The UE-to-networkrelay of claim 7, wherein the at least one processor is furtherconfigured to: transmit, to a core network entity via the transceiver,the information associated with the one or more QoS parameters.
 9. TheUE-to-network relay of claim 8, wherein the at least one processor isfurther configured to: update the PC5 QoS flow based on anauthentication by a policy control function (PCF) entity for the one ormore QoS parameters.
 10. The UE-to-network relay of claim 7, wherein theat least one processor is further configured to: receive, from a corenetwork entity via the transceiver, information associated with QoSmapping rules.
 11. The UE-to-network relay of claim 7, wherein theUE-to-network relay is pre-configured with information associated withQoS mapping rules.
 12. The UE-to-network relay of claim 7, wherein theinformation associated with the one or more QoS parameter is transmittedvia a layer-2 link modification procedure for modifying the PC5 QoSflow.